Create the charter for Kubeflow Community Distribution committee#951
Create the charter for Kubeflow Community Distribution committee#951juliusvonkohout wants to merge 3 commits intomasterfrom
Conversation
Added the charter for the Kubeflow Community Distribution committee, detailing its scope, roles, and collaboration expectations. Signed-off-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
juliusvonkohout
changed the title
Co-authored-by: Helber Belmiro <helber.belmiro@gmail.com> Signed-off-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com>
Added introductory statement about the committee's purpose. Signed-off-by: Julius von Kohout <45896133+juliusvonkohout@users.noreply.github.com>
|
|
||
| - The Kubeflow Community Distribution is a committee dedicated to provide a tested and integrated platform experience for the Kubeflow community. | ||
| The governance of the Kubeflow Community Distribution committee will evolve as the community grows, ensuring that the platform remains relevant and impactful. | ||
| - Promote the vision, values, and mission of the Kubeflow project in collaboration with the KSC, KOC, and WG Leads. |
There was a problem hiding this comment.
This should be part of the Charter, like for KOC and KSC: https://github.com/kubeflow/community/blob/master/KUBEFLOW-OUTREACH-COMMITTEE.md
|
|
||
| Kubeflow's [governance model](https://github.com/kubeflow/community/blob/master/wgs/wg-governance.md) includes a plethora of different leadership roles and is quite complex and designed for larger committes. This section aims to set requirements and expectations regarding tasks, roles and promotions. | ||
|
|
||
| **Subproject Owner**, **Technology Lead** or **Chair** roles were defined by trying |
There was a problem hiding this comment.
This should be technical lead?
| - Aid the kubeflow project maintainer regarding security best practices. | ||
| - Communicate with the kubeflow project maintainer regarding releases and versioning. |
There was a problem hiding this comment.
IMO security and releases should be separate
There was a problem hiding this comment.
So far in practice they are very tight together.
| - Improve the ease of deployment, packaging, and distribution of Kubeflow sub-projects across heterogenous environments. | ||
| - Empower external organizations to adopt, integrate, and build upon Kubeflow sub-projects within their own distributions. | ||
|
|
||
| ## Scope |
There was a problem hiding this comment.
This looks comprehensive. I wonder if there should be clearer separation of responsibilities with other committees. Otherwise this committee will be overwhelmed.
There was a problem hiding this comment.
That is actually the status quo task for the platform WG or what i am doing for years.
5 participants
Added the charter for the Kubeflow Community Distribution committee, detailing its scope, roles, and collaboration expectations.
@kubeflow/kubeflow-steering-committee